Techniques for behavioral pairing in a dispatch center system

ABSTRACT

Techniques for behavioral pairing in a dispatch center system are disclosed. In one particular embodiment, the techniques may be realized as a method for behavioral pairing in a dispatch center system comprising determining, by at least one computer processor communicatively coupled to and configured to operate in the dispatch center system, a dispatch request for a customer; determining, by the at least one computer processor, a plurality of field agents available to service the customer&#39;s dispatch request; determining, by the at least one computer processor, a model of preferred field agent-customer pairings based at least in part on historical field agent-customer interaction outcome data; selecting, by the at least one computer processor, one of the plurality of field agents based on the model; and outputting, by the at least one computer processor, the selection to facilitate dispatching the selected field agent to the customer.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/480,034, filed Apr. 5, 2017, which is hereby incorporated byreference in its entirety as if fully set forth herein.

FIELD OF THE DISCLOSURE

This disclosure generally relates to pairing dispatched field agentswith customers through dispatch centers and, more particularly, totechniques for behavioral pairing in a dispatch center system.

BACKGROUND OF THE DISCLOSURE

A typical dispatch center algorithmically assigns customers requestingservice to field agents available for assignment to those customers. Thedispatch center may include a contact center for receiving customerrequests (e.g., telephone calls, Internet chat sessions or forms,emails, text messages). The field agents may perform a variety of tasksin various sectors, such as cable installation for a telecommunicationscompany, claim adjusting for an insurance company, etc.

In some typical dispatch centers, customers are assigned to field agentsordered based on which field agent has been waiting the longest for anew dispatch, appointment availability, location, etc. Field agentsand/or customers may be assigned to each other on a first-come,first-served basis. This strategy may be referred to as a “first-in,first-out”, “FIFO”, or “round-robin” strategy.

In some advanced contact centers, contacts (e.g., callers) are pairedwith agents (e.g., phone agents) using a “behavioral pairing,” or a “BP”strategy, under which contacts and agents may be deliberately(preferentially) paired in a fashion that enables the assignment ofsubsequent contact-agent pairs such that when the benefits of all theassignments under a BP strategy are totaled they may exceed those ofFIFO and other strategies such as performance-based routing (“PBR”)strategies. BP is designed to encourage balanced utilization of agentswithin a skill queue while nevertheless simultaneously improving overallcontact center performance beyond what FIFO or PBR methods will allow.This is a remarkable achievement inasmuch as BP acts on the samecontacts and same agents as FIFO or PBR methods, utilizes agentsapproximately evenly as FIFO provides, and yet improves overall contactcenter performance. BP is described in, e.g., U.S. Pat. No. 9,300,802,which is incorporated by reference herein. Additional information aboutthese and other features regarding the pairing or matching modules(sometimes also referred to as “SATMAP”, “routing system”, “routingengine”, etc.) is described in, for example, U.S. Pat. No. 8,879,715,which is incorporated by reference herein. However, even these advancedcontact centers using BP dispatch field agents to customers using asuboptimal strategy such as FIFO. Field agents have numerousopportunities to deliver value to customers on behalf of theircompanies, such as customer satisfaction, up-selling and cross-selling,job completion time, etc., and under a FIFO pairing strategy, fieldagents will not be paired with customers so as to optimize dispatchcenter performance.

For example, in the television provider industry, a field technician maybe dispatched to a customer residence to install or repair access tocontent via satellite, fiber optics, coaxial cable, etc. During thecustomer interaction, the field technician may have an opportunity todevelop a rapport with the customer, thereby improving customersatisfaction with the installation or repair experience. The fieldtechnician may also have an opportunity to assess the customer's otherneeds and inform the customer about additional products or services(e.g., premium channel subscriptions, warranties, screen wipes, soundbars), generating additional up-sell or cross-sell revenue along withincreased customer satisfaction. Therefore, determining a preferredpairing between a field agent and a customer may increase the likelihoodof an optimal field agent-customer interaction over a typical FIFOpairing strategy.

In view of the foregoing, it may be understood that there is a need fora system that enables improving the efficiency and performance ofdispatch pairing strategies that are distend to choose among multiplepossible dispatch pairings such as a BP strategy.

SUMMARY OF THE DISCLOSURE

Techniques for behavioral pairing in a dispatch center system aredisclosed. In one particular embodiment, the techniques may be realizedas a method for behavioral pairing in a dispatch center systemcomprising determining, by at least one computer processorcommunicatively coupled to and configured to operate in the dispatchcenter system, a dispatch request for a customer; determining, by the atleast one computer processor, a plurality of field agents available toservice the customer's dispatch request; determining, by the at leastone computer processor, a model of preferred field agent-customerpairings based at least in part on historical field agent-customerinteraction outcome data; selecting, by the at least one computerprocessor, one of the plurality of field agents based on the model; andoutputting, by the at least one computer processor, the selection tofacilitate dispatching the selected field agent to the customer.

In accordance with other aspects of this particular embodiment, thedispatch request comprises at least one requested dispatch time, anddetermining the plurality of field agents available to service thecustomer's dispatch request is constrained based on the at least onerequested dispatch time.

In accordance with other aspects of this particular embodiment, thetechniques may further comprise selecting, by the at least one computerprocessor, at least one suggested dispatch time, wherein the selectedfield agent is available during the at least one suggested dispatchtime.

In accordance with other aspects of this particular embodiment, theselected field agent may be dispatched immediately or as soon aspracticable after the selection.

In accordance with other aspects of this particular embodiment, thetechniques may further comprise recording, by the at least one computerprocessor, results for a first plurality of field-agent customerinteractions paired using a behavioral pairing strategy; recording, bythe at least one computer processor, results for a second plurality offield-agent customer interactions paired using a FIFO pairing strategy;and outputting, by the at least one computer processor, a measure ofrelative performance between the behavioral pairing strategy and theFIFO pairing strategy based on the recorded results for the first andsecond pluralities of field-agent customer interactions.

In accordance with other aspects of this particular embodiment, thetechniques may further comprise updating, by the at least one computerprocessor, the model based at least in part on one or more of: theresults for the first plurality of field-agent customer interactions,the results for the second plurality of field-agent customerinteractions, and the measure of relative performance.

In accordance with other aspects of this particular embodiment, themodel may be based on a diagonal strategy.

In another particular embodiment, the techniques may be realized as asystem for behavioral pairing in a dispatch center system comprising atleast one computer processor communicatively coupled to and configuredto operate in the dispatch center system, wherein the at least onecomputer processor is further configured to perform the steps in theabove-discussed method.

In another particular embodiment, the techniques may be realized as anarticle of manufacture for behavioral pairing in a dispatch centersystem comprising a non-transitory processor readable medium andinstructions stored on the medium, wherein the instructions areconfigured to be readable from the medium by at least one computerprocessor communicatively coupled to and configured to operate in thedispatch center system and thereby cause the at least one computerprocessor to operate to perform the steps in the above-discussed method.

The present disclosure will now be described in more detail withreference to particular embodiments thereof as shown in the accompanyingdrawings. While the present disclosure is described below with referenceto particular embodiments, it should be understood that the presentdisclosure is not limited thereto. Those of ordinary skill in the arthaving access to the teachings herein will recognize additionalimplementations, modifications, and embodiments, as well as other fieldsof use, which are within the scope of the present disclosure asdescribed herein, and with respect to which the present disclosure maybe of significant utility.

BRIEF DESCRIPTION OF THE DRAWINGS

To facilitate a fuller understanding of the present disclosure,reference is now made to the accompanying drawings, in which likeelements are referenced with like numerals. These drawings should not beconstrued as limiting the present disclosure, but are intended to beillustrative only.

FIG. 1 shows a block diagram of a dispatch center system according toembodiments of the present disclosure.

FIG. 2 shows an example of a BP dispatching method according toembodiments of the present disclosure.

FIG. 3 depicts an example of a dispatch benchmarking method according toembodiments of the present disclosure.

DETAILED DESCRIPTION

FIG. 1 shows a block diagram of a dispatch center system 100 accordingto embodiments of the present disclosure. The description hereindescribes network elements, computers, and/or components of a system andmethod for simulating dispatch center systems that may include one ormore modules. As used herein, the term “module” may be understood torefer to computing software, firmware, hardware, and/or variouscombinations thereof. Modules, however, are not to be interpreted assoftware which is not implemented on hardware, firmware, or recorded ona processor readable recordable storage medium (i.e., modules are notsoftware per se). It is noted that the modules are exemplary. Themodules may be combined, integrated, separated, and/or duplicated tosupport various applications. Also, a function described herein as beingperformed at a particular module may be performed at one or more othermodules and/or by one or more other devices instead of or in addition tothe function performed at the particular module. Further, the modulesmay be implemented across multiple devices and/or other components localor remote to one another. Additionally, the modules may be moved fromone device and added to another device, and/or may be included in bothdevices.

As shown in FIG. 1, the dispatch center system 100 may include a centraldispatch 110. The central dispatch 110 may receive incoming customerrequests (e.g., requests from callers) or support outbound connectionsto customers via a telecommunications network (not shown). The centraldispatch 110 may include customer request routing hardware and softwarefor helping to route customer requests among one or more dispatchcenters, or to one or more PBX/ACDs or other queuing or switchingcomponents, including other Internet-based, cloud-based, or otherwisenetworked agent-customer hardware or software-based dispatch centersolutions.

The central dispatch 110 may not be necessary such as if there is onlyone dispatch center, or if there is only one PBX/ACD routing component,in the dispatch center system 100. If more than one dispatch center ispart of the dispatch center system 100, each dispatch center may includeat least one local dispatch (e.g., local dispatches 120A and 120B). Thelocal dispatches 120A and 120B may be communicatively coupled to thecentral dispatch 110. In embodiments, various topologies of routing andnetwork components may be configured to implement the dispatch centersystem.

Each local dispatch for each dispatch center may be communicativelycoupled to a plurality (or “pool”) of field agents. Each dispatch centermay support a certain number of field agents to be available forscheduling during a given time. At any given time, a field agent may beavailable and waiting to be dispatched to a contact (e.g., for immediatedispatch, or for an open appointment time at a future date and time), orthe field agent may be unavailable for any of a number of reasons, suchas already having been dispatched—or scheduled for a future dispatch—toanother customer. The dispatch center may also account for additionalfield agent activities such as travel time to and from the customer, andperforming certain post-dispatch functions such as logging informationabout the dispatch, or taking breaks.

In the example of FIG. 1, the central dispatch 110 routes customerrequests to one of two local dispatches via local dispatch 120A andlocal dispatch 120B, respectively. Each of the local dispatches 120A and120B are shown with two field agents each. Field agents 130A and 130Bmay be assigned or otherwise delegated to local dispatch 120A, and fieldagents 130C and 130D may be assigned or otherwise delegated to localdispatch 120B.

The dispatch center system 100 may also be communicatively coupled to anintegrated service from, for example, a third party vendor. In theexample of FIG. 1, dispatch BP module 140 may be communicatively coupledto one or more dispatches in the dispatch center system 100, such ascentral dispatch 110, local dispatch 120A, or local dispatch 120B. Insome embodiments, central or local dispatches of the dispatch centersystem 100 may be communicatively coupled to multiple dispatch BPmodules. In some embodiments, dispatch BP module 140 may be embeddedwithin a component of a dispatch center system (e.g., embedded in orotherwise integrated with a dispatch center component, or a “BP dispatchcenter”). The dispatch BP module 140 may receive information from adispatch component (e.g., local dispatch 120A) about field agentsassigned to the dispatch (e.g., field agents 130A and 130B) and aboutincoming customer requests via another dispatch component (e.g., centraldispatch 110) or, in some embodiments, from a network (e.g., theInternet or a telecommunications network) (not shown).

A dispatch center may include multiple pairing modules (e.g., a dispatchBP module and a dispatch FIFO module) (not shown), and one or morepairing modules may be provided by one or more different vendors. Insome embodiments, one or more pairing modules may be components ofdispatch BP module 140 or one or more dispatch components such ascentral dispatch 110 or local dispatches 120A and 120B. In someembodiments, a dispatch BP module may determine which pairing module mayhandle pairing for a particular customer or other contact. For example,the dispatch BP module may alternate between enabling pairing via thedispatch BP module and enabling pairing with the dispatch FIFO module.In other embodiments, one pairing module (e.g., the dispatch BP module)may be configured to emulate other pairing strategies. For example, adispatch BP module, or a dispatch BP component integrated with dispatchBP components in the dispatch BP module, may determine whether thedispatch BP module may use BP or emulated FIFO pairing for a particularcustomer request. In this case, “BP on” may refer to times when thedispatch BP module is applying the BP strategy, and “BP off” may referto other times when the dispatch BP module is applying a differentpairing strategy (e.g., FIFO).

In some embodiments, regardless of whether pairing strategies arehandled by separate modules, or if some pairing strategies are emulatedwithin a single pairing module, the single pairing module may beconfigured to monitor and store information about pairings made underany or all pairing strategies. For example, a dispatch BP module mayobserve and record data about FIFO pairings made by a FIFO module, orthe BP module may observe and record data about emulated FIFO pairingsmade by a BP module operating in FIFO emulation mode.

FIG. 2 shows an example of a BP dispatching method 200 according toembodiments of the present disclosure. BP dispatching method 200 maybegin at block 210.

At block 210, at least one customer dispatch request may be determined.For example, a customer may call a call center, and the call centeragent may assess the customer's needs and determine that a field agentshould be dispatched to provide technical service to the customer. Insome embodiments, an interactive voice response (IVR) system or otherautomated computer system may assess the customer's needs and/ordetermine the at least one customer dispatch request. After—or inparallel with—determining the at least one customer dispatch request, BPdispatching method 200 may proceed to block 220.

At block 220, available field agents may be determined. In someembodiments, available field agents may be limited to those field agentsthat are available for immediate (or otherwise near-term) dispatch tothe customer. In other embodiments, available field agents may belimited to those field agents that are available during the requesteddates or time windows requested by the customer, or to those fieldagents that are available during dates or time windows suggested by thedispatcher (e.g., a call center agent). In other embodiments, theavailable field agents may be any or all of the agents assigned orotherwise delegated to a particular dispatch center or dispatch queue(e.g., local dispatch), regardless of potential scheduling constraints.After determining available field agents, BP dispatching method 200 mayproceed to block 230.

At block 230, a dispatch BP model of preferred field agent-customerpairings may be determined, based at least in part on an analysis ofhistorical field agent-customer interaction outcome data. In someembodiments, historical outcome data, customer attribute data (e.g.,customer relationship management or CRM data), and/or third-party datamay be analyzed, and a computer-generated model of preferred fieldagent-customer pairings may be generated. In some embodiments, thedispatch BP model may be based on a diagonal strategy for BP. In someembodiments, the dispatch BP model may be used to increase the overallperformance of the dispatch center system while targeting a balancedutilization of field agents. After determining the dispatch BP model, BPdispatching method 200 may proceed to block 240.

At block 240, one of the field agents determined at block 220 may beselected for pairing to a customer whose request was determined at block210 based on the dispatch BP model determined at block 230. In someembodiments, such as those in which the available field agents may beany or all of the agents assigned or otherwise delegated to a particulardispatch center or dispatch queue (e.g., local dispatch), regardless ofpotential scheduling constraints, the BP dispatching method 200 maysuggest specific dates or time windows to the customer during which oneor more preferred field agents would be available.

The selected pairing may be outputted to another component of thedispatch center system or otherwise displayed or used to assign thefield agent and schedule the dispatch. After outputting the selectedfield agent-customer pairing, BP dispatching method 200 may end.

FIG. 3 depicts an example of a dispatch benchmarking method 300according to embodiments of the present disclosure. At block 310,dispatch benchmarking method 300 may begin.

At block 310, results for a first plurality of field agent-customerinteractions paired using a first pairing strategy of alternatingpairing strategies may be recorded or otherwise determined. For example,after a field technician finishes installing cable television service ina customer's home, the customer may be asked to rate the fieldtechnician's performance and answer other questions regarding customersatisfaction. In another example, a field technician may sell thecustomer additional products or services during the interaction, such asa warranty, a premium channel subscription, or a speaker system. Duringor after the interaction, the field technician may submit or otherwiserecord information about the sale. In another example, information aboutthe interaction outcome may be recorded automatically, such as theamount of time the field technician spent during the interaction.

In some embodiments, the alternating strategies may be BP and a FIFOpairing strategy, and the first pairing strategy may be BP. In theseembodiments, each of the first plurality of field agent-customerinteractions may have been paired using BP and thus have a likelihood ofimproving the overall performance of the dispatch center compared withpairing using FIFO. In some embodiments, pairing strategies mayalternate according to periodic cycling (e.g., cycling BP on and off).In some embodiments, the dispatch center system may cycle among morethan two pairing strategies.

After—or in parallel with—determining results for a first plurality offield agent-customer interactions paired using the first pairingstrategy, dispatch benchmarking method 300 may proceed to block 320.

At block 320, results for a second plurality of field agent-customerinteractions paired using the second pairing strategy of the alternatingpairing strategies may be recorded or otherwise determined. In someembodiments, the second pairing strategy may be FIFO or another non-BPpairing strategy. In these embodiments, each of the second plurality offield agent-customer interactions may have been paired using FIFO (oranother non-BP pairing strategy) and thus likely have a worse overallperformance of the dispatch center compared with pairing using BP. Afterdetermining results for the second plurality of field agent-customerinteractions paired using the second pairing strategy, dispatchbenchmarking method 300 may proceed to block 330.

At block 330, relative performance between the alternating pairingstrategies may be determined. For example, if the alternating pairingstrategies are BP and FIFO, dispatch benchmarking method may compare theperformance of the first plurality of interactions with the performanceof the second plurality of interactions. The relative performance mayrepresent a performance gain achieved using BP instead of FIFO. In someembodiments, such as those in which BP is provided by a third-partyvendor, payments to the third-party vendor may be calculated based atleast in part on the extent of performance gain actually measured over aperiod of time that is attributable to BP.

At this point it should be noted that behavioral pairing in a dispatchcenter system in accordance with the present disclosure as describedabove may involve the processing of input data and the generation ofoutput data to some extent. This input data processing and output datageneration may be implemented in hardware or software. For example,specific electronic components may be employed in a behavioral pairingmodule or similar or related circuitry for implementing the functionsassociated with behavioral pairing in a dispatch center system inaccordance with the present disclosure as described above.Alternatively, one or more processors operating in accordance withinstructions may implement the functions associated with behavioralpairing in a dispatch center system in accordance with the presentdisclosure as described above. If such is the case, it is within thescope of the present disclosure that such instructions may be stored onone or more non-transitory processor readable storage media (e.g., amagnetic disk or other storage medium), or transmitted to one or moreprocessors via one or more signals embodied in one or more carrierwaves.

The present disclosure is not to be limited in scope by the specificembodiments described herein. Indeed, other various embodiments of andmodifications to the present disclosure, in addition to those describedherein, will be apparent to those of ordinary skill in the art from theforegoing description and accompanying drawings. Thus, such otherembodiments and modifications are intended to fall within the scope ofthe present disclosure. Further, although the present disclosure hasbeen described herein in the context of at least one particularimplementation in at least one particular environment for at least oneparticular purpose, those of ordinary skill in the art will recognizethat its usefulness is not limited thereto and that the presentdisclosure may be beneficially implemented in any number of environmentsfor any number of purposes. Accordingly, the claims set forth belowshould be construed in view of the full breadth and spirit of thepresent disclosure as described herein.

1. A method for behavioral pairing in a dispatch center systemcomprising: determining, by at least one computer processorcommunicatively coupled to and configured to operate in the dispatchcenter system, a dispatch request for a customer; determining, by the atleast one computer processor, a plurality of field agents available toservice the customer's dispatch request; determining, by the at leastone computer processor, a model of preferred field agent-customerpairings based at least in part on historical field agent-customerinteraction outcome data; selecting, by the at least one computerprocessor, one of the plurality of field agents based on the model; andoutputting, by the at least one computer processor, the selection tofacilitate dispatching the selected field agent to the customer.
 2. Themethod of claim 1, wherein the dispatch request comprises at least onerequested dispatch time, and wherein determining the plurality of fieldagents available to service the customer's dispatch request isconstrained based on the at least one requested dispatch time.
 3. Themethod of claim 1, further comprising selecting, by the at least onecomputer processor, at least one suggested dispatch time, wherein theselected field agent is available during the at least one suggesteddispatch time.
 4. The method of claim 1, wherein the selected fieldagent is dispatched immediately or as soon as practicable after theselection.
 5. The method of claim 1, further comprising: recording, bythe at least one computer processor, results for a first plurality offield-agent customer interactions paired using a behavioral pairingstrategy; recording, by the at least one computer processor, results fora second plurality of field-agent customer interactions paired using aFIFO pairing strategy; and outputting, by the at least one computerprocessor, a measure of relative performance between the behavioralpairing strategy and the FIFO pairing strategy based on the recordedresults for the first and second pluralities of field-agent customerinteractions.
 6. The method of claim 5, further comprising updating, bythe at least one computer processor, the model based at least in part onone or more of: the results for the first plurality of field-agentcustomer interactions, the results for the second plurality offield-agent customer interactions, and the measure of relativeperformance.
 7. The method of claim 1, wherein the model is based on adiagonal strategy.
 8. A system for behavioral pairing in a dispatchcenter system comprising: at least one computer processorcommunicatively coupled to and configured to operate in the dispatchcenter system, wherein the at least one computer processor is furtherconfigured to: determine a dispatch request for a customer; determine aplurality of field agents available to service the customer's dispatchrequest; determine a model of preferred field agent-customer pairingsbased at least in part on historical field agent-customer interactionoutcome data; select one of the plurality of field agents based on themodel; and output the selection to facilitate dispatching the selectedfield agent to the customer.
 9. The system of claim 8, wherein thedispatch request comprises at least one requested dispatch time, andwherein determining the plurality of field agents available to servicethe customer's dispatch request is constrained based on the at least onerequested dispatch time.
 10. The system of claim 8, wherein the at leastone computer processor is further configured to select at least onesuggested dispatch time, wherein the selected field agent is availableduring the at least one suggested dispatch time.
 11. The system of claim8, wherein the selected field agent is dispatched immediately or as soonas practicable after the selection.
 12. The system of claim 8, whereinthe at least one computer processor is further configured to: recordresults for a first plurality of field-agent customer interactionspaired using a behavioral pairing strategy; record results for a secondplurality of field-agent customer interactions paired using a FIFOpairing strategy; and output a measure of relative performance betweenthe behavioral pairing strategy and the FIFO pairing strategy based onthe recorded results for the first and second pluralities of field-agentcustomer interactions.
 13. The system of claim 12, wherein the at leastone computer processor is further configured to update the model basedat least in part on one or more of: the results for the first pluralityof field-agent customer interactions, the results for the secondplurality of field-agent customer interactions, and the measure ofrelative performance.
 14. The system of claim 8, wherein the model isbased on a diagonal strategy.
 15. An article of manufacture forbehavioral pairing in a dispatch center system comprising: anon-transitory processor readable medium; and instructions stored on themedium; wherein the instructions are configured to be readable from themedium by at least one computer processor communicatively coupled to andconfigured to operate in the dispatch center system and thereby causethe at least one computer processor to operate so as to: determine adispatch request for a customer; determine a plurality of field agentsavailable to service the customer's dispatch request; determine a modelof preferred field agent-customer pairings based at least in part onhistorical field agent-customer interaction outcome data; select one ofthe plurality of field agents based on the model; and output theselection to facilitate dispatching the selected field agent to thecustomer.
 16. The article of manufacture of claim 15, wherein thedispatch request comprises at least one requested dispatch time, andwherein determining the plurality of field agents available to servicethe customer's dispatch request is constrained based on the at least onerequested dispatch time.
 17. The article of manufacture of claim 15,wherein the instructions further cause the at least one computerprocessor to operate so as to select at least one suggested dispatchtime, wherein the selected field agent is available during the at leastone suggested dispatch time.
 18. The article of manufacture of claim 15,wherein the selected field agent is dispatched immediately or as soon aspracticable after the selection.
 19. The article of manufacture of claim15, wherein the instructions further cause the at least one computerprocessor to operate so as to: record results for a first plurality offield-agent customer interactions paired using a behavioral pairingstrategy; record results for a second plurality of field-agent customerinteractions paired using a FIFO pairing strategy; and output a measureof relative performance between the behavioral pairing strategy and theFIFO pairing strategy based on the recorded results for the first andsecond pluralities of field-agent customer interactions.
 20. The articleof manufacture of claim 19, wherein the instructions further cause theat least one computer processor to operate so as to update the modelbased at least in part on one or more of: the results for the firstplurality of field-agent customer interactions, the results for thesecond plurality of field-agent customer interactions, and the measureof relative performance.